docs: document strict spot capacity behavior#246
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new strict spot capacity behavior for Karpenter-backed node groups. Spot node groups now provision spot instances only and no longer silently fall back to on-demand capacity, so users need to know when spot is appropriate and what guarantees the platform makes.
Changes
cloud-accounts/node-groups.mdxexplaining strict spot behavior, when to use it, when not to, and how to create a spot node group.Context
Triggered by an upstream change that tightens spot node pool configuration to spot-only (removing the implicit on-demand fallback). Existing pools written in the legacy mixed format continue to be recognized as spot and are rewritten in the strict format on the next reconciliation, so no user action is required.